Well, the last beta roundup is here, and yes, it includes the new and improved ColdBox Dashboard. So please enjoy this beta as it includes the following updates and enhancements: - ColdBox Dashboard 2.0.0 - Welcome to ColdBox IoC Object Caching: You can now enable the IOC plugin to cache your service objects in the coldbox cache. In order to do this, you will have to enable it in your config file via the 'IOCObjectCaching' flag. Then, you will need to get rid of your singletons in your IOC declartion files and declare your singletons via the cfcomponet tag using the 'cache=true' metadata attribute. You can also assign a timeout here. - Caching Debugging Panel Enhanced. - Coldspring now receives the coldbox controller reference as part of the settings structure. The gap in the model is now closed. You can now reference the active coldbox controller in your IoC configuration files by using '${Setting: coldbox_controller not found}'. You will now be able to use the framework in your model objects if needed. - AppMapping setting in the config file is now optional. If set in the config file, then it will override the auto-detected mapping. This is a great feature if your main application root is not reachable from the url. - The new object to use in the event handler methods and layouts/views is 'Event' to standardize with conventions. - All documentation updated to 2.0.0 - BlueDragon fixes - Minor fixes,updates. - Install ANT task, so you can refactor the code if needed. - Application Template ANT task. You can now create new applications via ANT. - More guides coming soon. You can find the beta in the forums as usual Well, enjoy this latest beta as the release is coming soon.
Blog
Recent Entries
Introducing bx-jwt: Enterprise-Grade JSON Web Tokens for BoxLang 🔐
JWT authentication is everywhere. But rolling it correctly — with proper algorithm enforcement, key management, clock skew handling, JWE encryption, and zero security footguns — is anything but trivial. Today, we're shipping bx-jwt, a production-ready JWT/JWE module for BoxLang that handles all of it out of the box, so you can focus on building, not fighting cryptography.
What “Modernize or Die” Really Means in 2026
“Modernize or Die” is not about forcing teams into MVC, chasing trends, or rewriting every CFML application from scratch. It means making sure your applications, teams, and processes can survive the future: easier to maintain, test, secure, deploy, document, hire for, and evolve. In 2026, modernization is less about adopting the newest pattern and more about reducing business risk, protecting the value already built into your systems, and ensuring CFML applications remain credible, sustai...
Free Webinar: Making AI useful for CFML/Java developers in Real Applications with BoxLang!
AI is everywhere right now, but for many development teams, the biggest question is no longer “What is AI?” it’s “How do we actually use it in real applications in a secure, practical, and maintainable way?”
Add Your Comment
(2)
Mar 18, 2007 07:16:49 UTC
by Sana
Hi Luis,
Its really great work, Would you like to explain one thing. below text from your post:
[You will now be able to use the framework in your model objects if needed].
Thanks
Mar 18, 2007 12:06:31 UTC
by Luis Majano
Sure Sana,
I can actually send the coldbox controller reference into a bean declaration by using the following property in coldspring: ${coldbox_controller}
Once I receive the controller in the model objects I can use it and tap into the framework. Let's say I wanted a setting: coldbox_controller.getSetting()
Let's say I wanted to use the AOP logging tool: coldbox_controller.getPlugin().logEntry(,)>
Now, some people will say, then you tie your object model to a framework. Well, the answer is YES!! That is my purpose, to extend into the object model and take over.
There are so many good things about it, I am using it anyways. So If I ever decide to go to another framework, probably means, ColdBox is not around anymore.
So expect more object model infiltrations by coldbox.